Skip to content

K8SPG-718 patroni metrics to pmm #1209

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

K8SPG-718 patroni metrics to pmm #1209

wants to merge 3 commits into from

Conversation

gkech
Copy link
Contributor

@gkech gkech commented Jul 4, 2025

K8SPG-718 Powered by Pull Request Badge

CHANGE DESCRIPTION

Problem:
The patroni metrics were not available in PMM. Given that patroni runs in TLS mode, we need to utilize an option that was added on PMM3.3 that skips the tls verification. The auto generated certificates do not contain the localhost 127.0.0.1 in its Subject Alternative Names (SANs).

The related feature will not be available in PMM2.

Cause:
Short explanation of the root cause of the issue if applicable.

Solution:

The e2e test for pmm3 is updated to query a selected patroni metric to verify that the integration is done properly.

Also visible through the PMM dashboard:

Screenshot 2025-07-07 at 11 00 25 AM

CHECKLIST

Jira

  • Is the Jira ticket created and referenced properly?
  • Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
  • Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

  • Is an E2E test/test case added for the new feature/change?
  • Are unit tests added where appropriate?

Config/Logging/Testability

  • Are all needed new/changed options added to default YAML files?
  • Are all needed new/changed options added to the Helm Chart?
  • Did we add proper logging messages for operator actions?
  • Did we ensure compatibility with the previous version or cluster upgrade process?
  • Does the change support oldest and newest supported PG version?
  • Does the change support oldest and newest supported Kubernetes version?

@gkech gkech force-pushed the K8SPG-718 branch 2 times, most recently from c811bad to da7f73c Compare July 4, 2025 11:45
@gkech gkech marked this pull request as ready for review July 7, 2025 07:50
@nmarukovich
Copy link
Contributor

nmarukovich commented Jul 7, 2025

looks good for me, waiting for cr version fix

@gkech
Copy link
Contributor Author

gkech commented Jul 8, 2025

the test failures both for e2e and unit are expected since we added this commit: 74c0851

@JNKPercona
Copy link
Collaborator

Test Name Result Time
backup-enable-disable passed 00:06:43
custom-extensions passed 00:08:38
custom-tls passed 00:04:57
demand-backup passed 00:24:39
finalizers passed 00:03:53
init-deploy passed 00:03:06
monitoring passed 00:07:34
monitoring-pmm3 failure 00:05:34
one-pod passed 00:05:45
operator-self-healing passed 00:08:45
pgvector-extension passed 00:02:26
pitr passed 00:12:07
scaling passed 00:05:01
scheduled-backup passed 00:33:19
self-healing passed 00:08:47
sidecars passed 00:02:39
start-from-backup passed 00:11:01
tablespaces passed 00:07:57
telemetry-transfer passed 00:03:19
upgrade-consistency passed 00:04:58
upgrade-minor passed 00:07:22
users passed 00:03:36
We run 22 out of 22 03:02:15

commit: 9af81c2
image: perconalab/percona-postgresql-operator:PR-1209-9af81c229

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants